Okay, think I may have figured this out on my own by accident while making a new custom form.So, when creating a custom form and adding fields you have an option to make that field a Checkbox or Choices. This is where a list can come into play.For my example I created a field called 'Change Type(s):' for a form to make changes to an employee. This was setup originally as a Choices field and then you can configure it to contain which choices you want available and the default choice. This works just fine.If you make a List however with all the items you want to populate that list with you would then select for that Field the specific list item you created. It would then populate all the items in the list instead of using the Checkbox/Choices option for that field.I see this as redundant though since you can make all the choices you want within the Form w/o needing to involve a List (which would require more upkeep to maintain different items all over the osTicket system). That being said if you create it as a list you can also fill in item properties via the Properties tab in the List. On the form you would not be able to create a description (on hover) for each choice but if you use a list you can create properties such as a description, examples, or notes that will apply to each item in the list individually and be available when you hover over the link once a ticket it made.Hopefully that makes some sense, I can add images if it would be helpful to anyone attempting to use Lists within their forms.